Access authentication and/or item process management using identification codes

ABSTRACT

Methods and systems using unqiue item identifiers and a wireless device to (a) authenticate authorization to take possession of an item and (b) specifying and/or tracking service processing of the item.

CROSS REFERENCE TO RELATED APPLICATIONS

This patent application is a continuation of co-pending U.S. patentapplication Ser. No. 15/447,238 filed Mar. 2 2017 entitled “AccessAuthentication and/or Item Process Management Using IdentificationCodes”, which is a continuation in part of co-pending U.S. patentapplication Ser. No. 14/597,813 filed Jan. 15, 2015 entitled “AccessAuthentication and/or Item Process Management Using IdentificationCodes” which claims priority to United States Provisional Patentapplication Ser. No. 61/928,666 filed Jan. 17, 2014 entitled “AccessAuthentication and/or Item Process Management Using IdentificationCodes”, the entire contents of each of which are hereby incorporated byreference.

BACKGROUND Technical Field

This patent application relates to electronic systems for managingaccess to an item and for services to be applied to an item.

Background Information

Certain businesses provide a service where a physical object owned bysomeone else is taken in for handling or processing and then returned.One such business is a laundry service. Institutions such asrestaurants, hotels and hospitals, delivery services, emergencyresponders, indeed any organization that dresses their public-facingpersonnel in uniforms, requires a constant flow of clean linens andgarments. A similar challenge is presented in a university or hotelvalet where there may be thousands of students or hotel guests needingtheir personal garments washed on a regular and timely basis.

Organized collection, sorting, laundering, packaging, and timely returnof articles in these environments is criticial to smooth operation ofthe institution as a whole.

It is also important to correctly associate a specific customer witheach piece of personal property being serviced so that items are notreturned to people who are not authorized to receive them.

A customer of such a service would also prefer to be notified of certainevents, such as the stage of processing, and when their items are readyto be picked up.

SUMMARY

In one implementation, a physical item that is to be submitted forhandling by a service provider is associated with a unique identifyingcode that is electronically readable, such as a Quick Response (QR)code. The electronic identifying code may be placed on the item itself,or placed on a container for the item. For example, in the case wherethe service is a laundry service, the identifying code is preferablyplaced on the outside of a laundry bag issued to an individual endcustomer.

In one example implementation, a customer having item(s) for service isexpected to have a smartphone or other personal portable computingdevice that is capable of

(a) executing a mobile application software program to interact with thecustomer;

(b) being electrically queried to retrieve a Universal Device Identifier(UDID) associated with the smartphone;

(c) taking a digital photo of the identifying code associated with theitem (laundry bag); and/or

(d) taking digital photos of the service item(s) themselves (such as agarment) to further support any special instructions to be used inrendering the service.

Prior to a customer dropping off their items for service, the smartphoneapplication is executed to initiate collection of information needed toinitiate a service order. Using the smartphone application, the customermay take pictures of any items needing special processing. For example,a picture may be taken of an article of clothing that is stained, andthat picture is stored with the special order instructions.

It is also possible to provide authentication before a customer ispermitted to take possession of a processed acticle. For example, oncethe articles are processed (laundered) by the service provider, they maybe returned to a pick up location. At this point, the customer arrivesto pick up their items and runs a smartphone application. Afterphysically identifying their items (for example, their laundry bag), thesmartphone is used to scan/electronically detect the unique itemidentification code (the QR code on the bag) and to upload the item IDand the smartphone UDID to a server. The service checks the item ID andUDID data pair against its stored information to verify the identity ofthe customer. At this point additional authentication information suchas an access code may be required to be provided via the smartphoneapplication. It is only after the verification and authentication of thecustomer is the customer permitted to take the item away from the pickup location.

The use of QR codes on or associated with the item itself also providesa way to track the progress items. For example, when items are droppedoff for service, the identifying code for the item may be scanned toinitiate automated tracking. From there, each state a laundering processcan be recorded, from laundry pickup through travel to a processingplant, through all laundering stages, to packaging, to return deliveryat the point where it is claimed by the customer. This allows for boththe operator and customer to have real-time insight into the status oflaundry orders at any point of the processing cycle.

Other features and advantages will become evident after reviewing thedetailed description that follows.

BRIEF DESCRIPTION OF THE DRAWINGS

The description below refers to the accompanying drawings, of which:

FIG. 1 is a high level graphic depiction of a laundry service from theperspective of an end customer;

FIG. 2 is a work flow for initiating a new laundry service order;

FIG. 3 is a work flow from the perspective of the laundry serviceprovider;

FIG. 4 is a work flow for a returning customer picking up their laundry;

FIG. 5A is a sequence diagram for an authentication process;

FIG. 5B is a sequence diagram for a dropoff and pickup process;

FIG. 6 is an example data structure for a customer record; and

FIG. 7 is an example data structure for an order record.

DESCRIPTION OF AN EXAMPLE EMBODIMENT

As will be understood after reviewing the detailed description below, asystem and method can be provided that uses electronically readableidentifying information

(a) placed on an item, such as a Quick Response (QR) code, bar code orother information that identifies the item, in connection with

(b) authentication data, such as unique identifier for a personalportable computing device associated with the customer (that is, thesmartphone's unique device identifier (UDID)), data made available bythe smartphone via Near Field Communication (NFC) or some otherprotocol, and/or a unique identifier for the customer, such as abiometric (fingerprint, photograph, signature), or some otherinformation that identifies the customer, such as a passcode. The itemidentifier and authentication data are used for the purpose ofidentifying and authenticating the owner or other authorized person toaccess the physical item at the time it is dropped off and/or isclaimed, as well as to track the status of submitting that same itemthrough a service process.

A particular implementation for tracking a laundry bag item is discussedbelow. This implementation illustrates the use of the system and methodfrom both the perspective of a customer of a laundry service as well asthe perspective of a laundry service provider, and describes a sequenceof operations performed by associated smartphones, servers, anddatabases. It will be understood however that other types of servicesthat take in articles to be processed can make use of the techniquesdescribed herein.

FIG. 1 generally illustrates a smartphone driven laundry service fromthe perspective of a customer. Here a customer 110 (who, for example,may be a college student or other institutional customer) brings theirdirty laundry 112 and smart phone 114 to a drop-off location 120. Thecustomer may have been assigned a scheduled date and time to drop offtheir laundry at location 120, or the time may be been chosen by thecustomer. The customer 110 has previously signed up to use a laundryservice 140 either by using their smartphone 114 or via some otherinternet-capable device. The sign up process can be through any knownprocess. The customer 110 may for example have previously interactedusing their smartphone 114 with a server (called a service providerserver 130 herein) to provide certain personal information such as theirname and contact info, and billing information such as a payment, whichis then stored in database 150.

During the sign-up process, the personal information for customer 110 isidentified and associated in the database 150 with a customer recordthat may include (i) an identifier their smart phone 114. During theprocess, or at some later time such as at the drop off location, such asby storing (a) the item identifier for the laundry bag 112 and someother authentication information such as a unique device identifier(UDID) for the customers' smartphone 114, NFC data generated by thesmartphone 114, and/or (b) customer authentication information such as abiometric or a passcode given to the customer.

An identifier tag 116 may carry the item identifier associated with thelaundry bag 112. The tag 116 may thus conveniently takes the form of aQR code, barcode, or other visual indcia for the item which can bedigitally scanned or otherwise electronically detected by the smartphone114 camera or other available scanning device. The indicia associatedwith the tag 116 may be printed or located on or within the bag itself,or may be printed or located on a fob attached to the bag. The tag 116may thus either be permanently or temporarily associated with the bag,depending on the needs of the customer 110 and/or the laundry serviceprovider.

In one example implementation, a clerk 122 is located at the drop-offlocation 120 and assures orderly collection (and later delivery) oflaundry bags from and to multiple customers 110. The clerk 122, viamobile device and software application running on a computer, tablet, orsmartphone 124, scans or electronically detects the unique QR code onthe tag 116 of the laundry bag 112 for the customer 110 that is bringingtheir laundry for processing. This detection of the QR code (or otheritem identifier) is forwarded and stored in database 150 and canrepresent liabaility transfer of the laundry items from the customer 110to the laundry service 140. From the perspective of the customer 110,all they typically need to interact with is the clerk 122 at the pick-uplocation and their smartphone 114.

In other embodiments, the drop-off location 120 may be an electronicallycontrolled lock box 127 that is not attended by a clerk 122. In thatarrangement, the customer 110 may gain access to the lock box 127 at anytime (or only at scheduled times) by arriving at the drop off location120. The customer 110 then calls up the smartphone application toexchange information wirelessly and electronically to identifythemselves and to cause the lock box 127 to unlock. The unlocking mayoccur, for example, electronically via commands sent by server 130 tothe lock box 127, or by an unlock code to the customer via thesmartphone application which is then used to manually manipulate a lockon the box 127.

The customer 110 themselves can then scan the tag 116 and deposit thebag 112 in the lock box 127. This event can be detected and reported tothe server 130. An access code or password may also be associated withthe lock box 127 and scanned or typed into the smartphone 114application by customer 110 to access the lock box 127 and/or informserver 130 that a bag has been dropped into the lock box 127. In anyevent, the server 130 can now record the fact that the lock box location127 has a new bag 112 now needing laundry services.

In instances where a lock box 127 is used for dropoff, system generatedpasscodes may be used for both authentication and/or authorization ofthe customer. The drop off and pick up locations may include more thanone lock box 127 that are shared from time to time among differentcustomers.

In one implementation using a lock box 127, the smart phone 114application may further assist with instructing the customer 110 on howto proceed. For example, the information exchanged with the customer 110may indicate which of several locations currently have available emptylock boxes 127. Here, the information exchanged may include asystem-generated passcode that can be used to access the lock box 127.The passcode may be made unique to the both the available location andthe tag 116 that was previously associated with the customer's bag 112.

If a passcode is used for authentication, it may be generated in manydifferent ways. It may be a short pass code of four or five digits, butshorter or longer. It may use alphanumeric characters and not justdigits. Passcodes may also be permanently assigned to a customer asopposed to being generated on each transaction.

It is also possible that passcodes are not used at the lockbox locationfor authentication, but rather other authentication data such as NearField Communications (NFC), Bluetooth, or other technologies that allowsthe customer's smartphone to communicate directly with and be uniquelyidentified by the lockbox system. Thus, there are other ways to causethe lockbox to unlock without the customer having to utilize a kiosk ora passcode.

Other information may also be collected for authentication of thecustomer, in the place of, or in addition to that mentioned above, suchas biometrics provided by the user (a fingerprint, facial photograph,signature, etc.)

Upon arrival at a location of an available lock box 127, the customerthen provides the passcode or other authentication information to gainaccess. The passcode or other authentication may be provided such as viaa kiosk at the lock box location or in some other way (such as via thesmartphone 114). The customer then places their bag in 112 in anyavailable open lock box 127 and closes the lock box 127. The customer110 may then use the smartphone 114 to report that they have droppedtheir bag 112 off for service.

A number of other systems and entities exist behind the scenes that theend customers 110 do not typically see.

For example, at a subsequent time a laundry service provider 140 sends avehicle 142 to the drop off location 120 to retrieve multiple laundrybags 112. The vehicle 142 transports the bags to a laundry processingplant 144 containing laundry machines 146. It is understood that the QRtags 116 on the bags 112 may at various times be further scanned. Forexample, the clerk 122 or driver of the vehicle 142 may scan them asthey are loaded onto the vehicle 142 at the drop off location 120, orthey may be scanned as part of intake processing at the plant 144, whenitems are processed by the laundry machines 146 or at other instancesand places. The additional scanning information enables the serviceprovider server 130 or other data processing machine such as one or moreother machine(s) 160 to keep track of the status of each laundry bag112. In different implementations, other data processing machines (s)160 may access the database 150 through the service provider server 130or may have direct access to database 150. For example, a laundryservice operator version of the software applicationlocated at plant 144may be used by service personnel to review order status and orderdetails, such as to carry out any special processing instructions.

At some point the laundry is processed 146, and the clean items areshrink wrapped with the bag 112 on top (or the shrink wrapped laundry isplaced inside the bag) in any case, so that the QR code 116 is visible.The vehicle 142 then returns to the drop off location with the processedbags 112.

At this subsequent time, which may be a prearranged time or in responseto receiving a message that the laundry is ready, the customer returnsto location 120 (or some other designated location). At this time thecustomer 110 (with or without help from clerk 122) identifies theirlaundry bag 112 from among many other laundry bags that may have beendropped off. This identification by the customer may be recognizing ahuman-readable label 118 on the bag 112 such as a name tag. Having theQR code and other identification on a single ID tag is advantageous, sothat it becomes more difficult to have bags switched/lost/etc. Thecustomer 110 then again scans the QR code 116 on the identified bag 112with their smart phone 114. The smartphone 114 and service providerserver 130 then exchange information (UDID, QR Code, and authenticationinformation, etc.) to confirm that the customer 110 is indeedauthenticated as the owner of the bag 112 and provides a visual and/oraudible indication to that effect. Upon recognizing the confirmation,the clerk 122 can now confirm that it is approved for the particularindividual appearing before them in person to claim possession of thebag 112. The claimed status of the laundry order is now stored in thedatabase 150 to represent liability transfer from laundry service 140 tocustomer 110.

In the case where lock boxes 127 are used to return the bag 112 to thecustomer 110, the notice provided via the smartphone 114 that laundry isready for pickup may include notification of the pickup location. Thisnotification may also include a system generated passcode if that isbeing used for authentication. The passcode may be unique to a specificlock box 127 (or locker) and the customer's bag 112. The notice may bedelivered via a smartphone application, text message, email, pushnotifications, or in other ways.

The customer then travels to the pickup location and provides theauthentication data (such as the passcode or their biometrics, or byautomated reading of the UUID or NFC data from their smartphone) to thesystem. The passcode, if utilized, may be entered into a kiosk locatedat the lock box location on via the mobile application. Onceauthenticated to the system, the customer is then provided withinformation as to which specific lock box 127 their bag 112 is in, andgiven access to that lock box in some way, such as by unlocking it. Thecustomer then picks up their bag 112, and may then again use thesmartphone 114 to indicate to the system that they have picked up theirbag 112. Alternatively, the lock box system can communicate to theserver provider 130 that the bag has been picked up and that particularlock box is now available for use by another customer.

FIG. 2 is a more detailed view of an example work flow performed when acustomer 110 is beginning a new laundry order. From an initial state 200the customer 110 realizes that they have laundry to be processed instate 202. In state 204 the customer collects their laundry. In state206 if no special processing instructions are needed for the itemscollected, then the customer can proceed to state 220.

However if any of the items require special processing then a state 208is entered. Here the customer accesses a website operated by the serviceprovider server 130. This access may typically occur on the smartphone114 using a mobile application. In state 210 the customer starts a neworder in the context of the mobile application and may in state 212select a type of garment to be processed. In state 214 the customer mayindicate the special instructions for the garment. The specialinstructions may include for example indicating the garment is to be drycleaned, spot treated, ony light starched, etc. Certain specialinstructions may activate additional charges processing in the mobileapplication, but other special instructions may not activate specialcharges.

In state 216 certain special instructions may request the customer 110to take a photograph of the garment. For example, if a stain on thegarment is to be spot treated the customer 110 may be asked to take apicture of the location surrounding the stain on the garment. In state217 the picture is taken using the smartphone and saved as part of theorder instructions being collected by the application running on thesmartphone 114. In this step, the photograph may be itself annotated,such as by electronically circling, marking, or otherwise indicating thestained area on the picture of the garment needing attention.

Processing returns in either event to state 218, where if more garmentsneed special instructions then state 212 is entered again. However, ifno more garments need special instructions, then processing proceedsthrough state 219. The order with special instructions can be submittedat this time, or maintained by the smartphone 114 until a later time,such as when the customer arrives at the pickup location 120. In thisstep, the order details including any special instructions and/orphotographs of articles are sent to an electronic order processingsystem such as via service provider server 130 and/or another server160, and billing can occur at this point as well. Note that the specialinstructions and taking of photographs, etc., is conveniently done backin the dormitory or at home, before the appointment time. Thus at theappointment time, all the customer needs to do is to drop off the bag112 and optionally confirm drop off with their smartphone 114.

In state 220 the customer can then fill the bag with the laundry itemsand in state 220 proceed to the drop off point 120. If the customer hadno special processing instructions, then a standard order is initiated.Order initiation may typically by the customer interacting with theirsmartphone application, which can happen anytime prior to the bag 112being left at the pick up location 120. Optionally, even if the customerdoes not initiate an order via their smartphone 114, a standard ordermight also be initiated at the time the bag 112 is scanned when it isloaded onto vehicle 142 or arrives at plant 144.

FIG. 3 is a sequence of workflow events that may occur from theperspective of the laundry service provider 140. In a first state 302 acustomer 110 arrives at the drop-off location 120 (at an appointed timeor some other time the location 120 is open for business) and leaves alaundry bag 112. At some later point in time in state 304 a driverarrives at the drop-off location. Here the driver will scan the laundrybags 112 before or while loading them on the vehicle. In state 306 thebags are then delivered to the plant 144.

In state 308 the garments are processed at the plant. In state 310 anydetails for any special items are identified, such as by laundry servicepersonnel accessing database 150 via the order information via otherserver(s) 160. If any items require special processing then laundryservice personnel can access digital photographs associated with theorder such as via computer, tablet, smartphone, or other device 190located in the processing plant 144. The photographs can be retrieved toensure that special instructions are properly carried out as previsoulyindicated for each specially handled garment by the end customer 110 whodirectly did so. Finally in a state 314 the laundry order is packagedwith the bag 112 for return delivery to the drop off location 120.

FIG. 4 is a sequence of events that occur when the laundry is returnedto a manned drop off location 120 in a state 400. At some later time instate 402 the customer arrives such as at an appointment time to pick uptheir bag 112. In state 404 customer 110 identifies their laundry bag112 such as by visually noting their name tag 118 on the side of a bagfrom among a number of bags that may be present.

Once the customer 110 finds their bag 112 they then initiate anauthentication process, such as by scanning the QR code 116 on the bag112 with the application running on a smartphone 114. The QR code andthe UDID electronically stored by the smartphone are then sent to theservice provider server 130. The service provider server 130 thenproceeds to a state 408 where an authentication process using the QRcode and UDID is performed. It is possible at this point, before state408 that additional authentication such as a passcode (such as fourdigit Personal Identification Number (PIN)) may be requested in state407. This passcode may be entered by the customer 110 via the smartphone114 and passed to the server 130 with the QR code and UDID in state 408.

In a state 410 it is determined if there is a match between the QR codescan and the UDID (and the passcode/PIN, if included) with the storedprior records for the order in process for that particular bag 112. Ifthere is a match, then a positive visual and/or aural indication can bepresented in state 412 on the smarphone 114 and shown to the clerk 122.The indication is taken by the clerk that the system has confirmed thatit is OK for the person who has scanned the bag to take possession ofthe bag. In state 414 the confirmation notation that the bag has beenpicked up may be entered in the database maintained by the serviceprovider server 130 for the purpose of tracking the state of the order.

If however back in state 410 there was no match between the QR code andUDID, or a failure of the passcode/PIN, indicating that the bag shouldnot be taken, then a number of following states 416 can entered. For astate 420 may be entered where a question is asked via the smartphone toconfirm if the user is trying to pick up a laundry bag. This can providethe customer a “way out” of a deviation in the normal expected pickupprocess flow; if they scanned an incorrect bag, an option can bepresented for them to try again. Alternatively an optional state 422 canbe entered in which the service can assume that the person scanning thebag is not yet a customer of the service, and an advertisement for theservice can be presented on the smartphone. Also, an optional state 424can be entered in which a display can be presented on the smart phonetelling the customer that their bag has been delayed in processing.Also, in state 426, a screen may be optionally displayed allowing theuser to indicate that some apparent mistake was made with the laundryprocessing (for example a garment was damaged) that will need furtherattention. However, this may also occur after the customer leaves thepick-up location, such as when the customer returns home and opens upthe bag to inspect the processed laundry items.

Still other states 430 may be entered by the system to process anyleftover bags that are not picked up at the appointment time. These maybe noted by the clerk 122 scanning the leftover bags with the othercomputer 124 which may be a tablet. This information can then be enteredinto the service provider server 130 to keep track of the fact that theprocessed laundry bags were not picked up as expected at the appointmenttime.

FIG. 5A is a sequence diagram for messages exchanged between and/oractions performed by the customer 110, the customer's smartphone 114,the service provider server 130, and the database 150. This sequencediagram indicates the authentication process flow using a pin orpasscode (which controls access to higher level secured functions suchas “Laundry Pickup” via an application tiered security implementationmodel) coupled with the QR Code and the UDID to authtenticate andauthorize the customer 110 to take possession of laundry bag 112.

In a first state 501 the customer 110 opens the application on theirsmartphone 114, and in state 502 the smartphone loads the smart phoneapplication. In state 503 the user enters an input within the context ofthe application such as by clicking on a request to pick up theirlaundry. A test is then performed to determine if the user session isauthenticated in step 504; if the session is already authenticated instate 505 then in state 520 the laundry pickup page is displayed;otherwise, if the session is not already authenticated in state 505 thena passcode entry page is displayed on the mobile device in state 506.The customer then enters a passcode in state 507 which is then passedfor validation in state 510 along with the UDID for the mobile phone instate 511. If the validation code returned in state 512 and 513 isinvalid in state 514, then a passcode entry page can be displayed instate 515. These steps can be repeated in state 516 if further necessaryto validate passcode entry.

In state 520 a point is reached where a pick up laundry page isdisplayed on the smartphone device 114. The customer then uses thesmartphone 114 to focus on and scan a QR code of the bag 112 in state521. Here the smartphone may capture the QR code such as via a digitalphotograph. The application next, in state 522, deciphers the QR codefrom the photograph and forwards it to the server 130. At state 523 theQR code (and optionally UDID) are sent through a network connection suchas the Internet to the database 523. The database 523 maintains amapping of these values as authentication factors and then returns a QRvalidation code in state 524. This QR validation code is then returnedto the smartphone in state 525. If the QR code is valid in state 526then a visual indication of acceptance of the customers request to pickup the bag is displayed in state 527 on the smartphone 114.

At this point in state 528 the customer 110 shows the visual indicationof acceptance to the clerk 122 for confirmation and then the customermay claim the laundry bag and accept it; alternatively visual indicationof rejection of the customers request to pick up the bag is displayed tothe customer 110 in state 529. If the acceptance is rejected, then asequence of states 530 and 531 and 532 may be repeated to try tosuccessfully complete the pick up process again.

FIG. 5B illustrates a similar sequence of messages exchanged betweenand/or actions performed by the customer 110, the smartphone 114, andthe service provider sytem 130, when an unmanned lock box system is usedto coordinate dropoff and pickup. In general, system-generated valuesuch as passcode (or other authentication data such as NFC orbiometrics) is used in certain steps of the process to indicate statusand authorization; in this implementation, the passcode may depend onthe lock box location and the bag identifier.

In a first state 550, the customer 110 starts the smartphone applicationand indicates they have laundry to be processed. As before, the customerthen uses their smartphone in state 551 to capture a QR code or otheridentifier for the bag 112 and the captured identifier is reported instate 552 to the system, and the system acknowledges receipt of the itemidentifiter in state 553.

In state 555 (which may occure before or after the customer scans thebag), the customer 112 also uses the smart phone application to requestthe availability of an open lock box at a nearby locker location. Instates 556 and 557 available locations are reported to and the selectedby the customer (based on the availability of an empty lock box 127).

At this point in state 558, the system generates a unique randompasscode (which may be 5 digits long). This passcode

is preferably unique to both the available lock boxlocation and the bag112; that is, the passcode only works for the selected location and isassociated with the identifier for the particular bag 112. This passcodeis then presented to the customer via the smartphone in state 559.

In state 560, the customer takes her bag 112 to the location of theavailable locker system and, using an input device such as a kiosklocated at the locker system, then enters the dropoff passcode toauthenticate themselves. Alternatively, the customer may use theirsmartphone to present the code via Near Field Communications orBluetooth or via the internet. Additionally the customer may usebiometrics provided by the user (a fingerprint, facial photograph,signature, etc.) to cause the lock box to be unlocked and or biometrics.

In state 561, the customer selects any available lock box 127, opensthat lock box 127, places their bag 112 inside, and closes it. In state562, the customer uses the kiosk (or clicks OK on their smartphone) toconfirm drop off to the service provider system 130; in state 563, anacknowledgement of the drop off may be returned to and displayed on thecustomer's smartphone. It is possible that information initiallydisplayed on the kiosk can be later viewed on the smartphone.

In state 570, the system is now aware that the bag 112 needs processing,and the bag is eventually picked up, processed, and returned as in theimplementations described previously.

In state 580, the customer 110 is notified that their bag 112 is readyand has been delivered to a lock box 127. At this point, the specificlock box 127 may not necessarily be identified to the customer, just thelocation of the lock box.

In state 582, in a case where the authentication information is anotherunique system generated passcode, that information is provided to thecustomer, or some. This passcode may be unique to a specific lock box127 in which the customer's bag 112 has been placed and which isassociated to the identifier for that bag 112.

The customer travels to the pickup location, and in state 584 using aninput device such as a kiosk located at the lock boxes, enters thepickup passcode to authenticate themselves. In state 585, the customeris told which lock box has their bag, either via the kiosk or theirsmartphone, opens the lock box, takes their bag out, and then closes thelock box.

It should be understood that in other embodiments, where theauthentication information is NFC- or device-specific, or based on userbiometrics, a different information exchange takes place.

In state 586, once authentication is complete, the customer may thenindicate to the service provider system they have picked up their bagsuch as by clicking on the smartphone application, and the system mayacknowledge that in state 588.

System operation with both manned drop-off/pick up location and anunmanned lock box locations have been described above. However otherarrangements are possible, for example:

-   -   Static Manned Dropoff and Pickup Location (the locations being        “Static” refers to a desk or other location that stays in the        same place day after day)    -   Mobile Manned Dropoff and Pickup Location (i.e. “Mobile”        refering to a collection vehicle that moves between locations        based on a communicated schedule)    -   Drop Bin Location with Manned Pickup Location (i.e. “Drop Bin”        refers to a location like a Goodwill type collection bin that is        sized to accommodate more than 1 bag at a time)    -   Lockbox Dropoff and Pickup Location (i.e. “Lockbox” refers to a        locker type system where each receptacle is sized to only handle        1 bag at a time)    -   Handoff of the bag between the customer and an independent        representative of the laundry service (such as an Uber driver).    -   Variations using the above can also be supported.

FIG. 6 is an example data structure for the information in a customerrecord maintained in the database 150.

FIG. 7 is an example data structure for the information in an orderrecord in the database 150.

Implementation Options

It will be understood that the data processing elements such as thewireless devices, smartphones, servers, file systems, and databasesdescribed herein may further include infrastructure elements that arenot shown, such as other types of physical networking equipment such asrouters, switches, and firewalls, or other data processing equipmentsuch as servers, load balancers, storage subsystems, and the like. Theservers may include web servers, database servers, application servers,storage servers, security appliances or other type of machines. Eachserver typically includes an operating system, application software, andother data processing services, features, functions, software, and otheraspects.

It should be understood that the example embodiments described above maybe implemented in many different ways. In some instances, the varioussmartphones and servers include “data processors” that may each beimplemented by a physical or virtual general purpose computer having acentral processor, memory, disk or other mass storage, communicationinterface(s), input/output (I/O) device(s), and other peripherals. Thegeneral purpose computer is transformed into the processors and executesthe processes described above, for example, by loading softwareinstructions into the processor, and then causing execution of theinstructions to carry out the functions described. Network interface(s)allow the computer to connect to various other devices attached to anetwork. Memory provides volatile storage for computer softwareinstructions and data used to implement an embodiment. Disk or othermass storage provides non-volatile storage for computer softwareinstructions and data used to implement, for example, the variousprocedures described herein.

Embodiments may therefore typically be implemented in hardware,firmware, software, or any combination thereof.

In certain embodiments, the procedures, devices, and processes describedherein are a computer program product that provides at least a portionof the software instructions for the system. Such a computer programproduct can be installed by any suitable software installationprocedure, as is well known in the art. In another embodiment, at leasta portion of the software instructions may also be downloaded over acable, communication and/or wireless connection. Embodiments may thusalso be implemented as instructions stored on a non-transientmachine-readable medium, which may be read and executed by one or moreprocedures. A non-transient machine-readable medium may include anymechanism for storing or transmitting information in a form readable bya machine (e.g., a computing device). For example, a non-transientmachine-readable medium may include read only memory (ROM); randomaccess memory (RAM); magnetic disk storage media; optical storage media;flash memory devices; and others.

It should therefore be appreciated that such descriptions containedherein are merely for convenience and that such actions in fact resultfrom computing devices, processors, controllers, or other devicesexecuting the firmware, software, routines, instructions, etc.

It also should be understood that the block and network diagrams mayinclude more or fewer elements, be arranged differently, or berepresented differently. But it further should be understood thatcertain implementations may dictate the block and network diagrams andthe number of block and network diagrams illustrating the execution ofthe embodiments be implemented in a particular way.

While this invention has been particularly shown and described withreferences to example embodiments thereof, it will be understood bythose skilled in the art that various changes in form and details may bemade therein without departing from the scope of the inventionencompassed by the appended claims.

What is claimed is:
 1. A method for handling a container that holds oneor more articles to be processed for a customer comprising: collectingthe container from one of several lock boxes; processing the articles;preparing the container and articles to be returned to the customer;sending authentication information to the customer, the authenticationinformation related to at least one of either the customer or thecontainer; placing the container in a lock box; locking the lock box;receiving input information; and when the input information correspondsto the authentication information, unlocking the lock box.
 2. The methodof claim 1 wherein sending authentication information further comprisessending authentication information to a wireless device associated withthe customer; and receiving input information further receives inputinformation via a kiosk associated with the lockbox.
 3. The method ofclaim 1 wherein sending authentication information further comprisessending authentication information to a wireless device associated withthe customer; and receiving input information further receives inputinformation via a near field communication (NFC) receiver associatedwith the lock box.
 4. The method of claim 1 wherein sendingauthentication information further comprises sending authenticationinformation as a scannable code to a wireless device associated with thecustomer; and receiving input information further receives inputinformation by scanning the scannable code.
 5. The method of claim 1wherein sending authentication information further comprises sendingauthentication information to a wireless device associated with thecustomer; and the wireless device further communicates with a lockboxcontroller to unlock the selected lockbox.
 6. The method of claim 1wherein receiving input information further comprises entering the inputinformation into a kiosk using a manual input device.
 7. A method totrack a container that holds one or more items to be processed for acustomer comprising: electronically scanning the container with awireless device to detect an identification code for the container;using the wireless device, sending the identification code to a server;processing the one or more items; sending authentication information tothe customer that depends on at least one of the identification code forthe item, an identification code for the customer, or a wireless deviceassociated with the customer; receiving input information; and when theinput information matches the authentication information, providing thecustomer with access to the one or more items.
 8. The method of claim 7additionally comprising: after processing the one or more items; placingthe one or more items in a lock box; and when the input matches theauthentication information, providing access to the one or more items byunlocking the lock box.
 9. The method of claim 8 wherein sendingauthentication information further comprises sending authenticationinformation to a wireless device associated with the customer; andreceiving input information further receives input information via akiosk associated with the lock box.
 10. The method of claim 8 whereinsending authentication information further comprises sendingauthentication information to a wireless device associated with thecustomer; and receiving input information further receives inputinformation via a near field communication (NFC) receiver associatedwith the lock box.
 11. The method of claim 8 wherein sendingauthentication information further comprises sending authenticationinformation as a scannable code to a wireless device associated with thecustomer; and receiving input information further receives inputinformation by scanning the scannable code.
 12. The method of claim 8wherein sending authentication information further comprises sendingauthentication information to a wireless device associated with thecustomer; and the wireless device further communicates with a lock boxcontroller to unlock the lock box.
 13. The method of claim 8 whereinreceiving input information further comprises entering the inputinformation into a kiosk using a manual input device.
 14. A method fortracking a container containing one or more articles of clothing througha process implemented by a laundry service provider for a customercomprising: receiving a device unique identifier for a wireless deviceassociated with the customer; electronically scanning the container todetect an identification code for the container; sending the deviceunique identifier and the identification code for the container to aserver; receiving a verification from the server; and providing a visualand/or audible indication of the verification.
 15. The method of claim14 wherein the electronically scanning step is performed with thewireless device associated with the customer.
 16. The method of claim 14additionally comprising: processing the articles of clothing; before thearticles of clothing are returned to the customer; reading a secondunique identifier directly from the wireless device associated with thecustomer; and when the device unique identifier and the second uniqueidentifier match, providing access to the articles of clothing by thecustomer.
 17. The method of claim 14 wherein access to the articles ofclothing is controlled by an electronic lock box.
 18. The method ofclaim 14 additionally comprising: sending authentication information tothe wireless device associated with the customer; and placing thecontainer in a lock box; locking the lock box; receiving inputinformation; and when the input information corresponds to theauthentication information, unlocking the lock box.
 19. The method ofclaim 18 wherein receiving input information further receives inputinformation via a kiosk associated with the lockbox.
 20. The method ofclaim 18 wherein receiving input information further receives inputinformation via a Near Field Communication (NFC) receiver associatedwith the lockbox.
 21. The method of claim 18 wherein sendingauthentication information further comprises sending authenticationinformation as a scannable code to the wireless device associated withthe customer; and receiving input information further receives inputinformation by scanning the scannable code at a location associated withthe lock box.
 22. The method of claim 18 wherein the wireless devicefurther communicates with a lockbox controller to unlock the selectedlockbox.